X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C81BEF.F909B5B4@onstor-exch02.onstor.net>; Wed, 31 Oct 2007 11:58:06 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C81BEF.F909B5B4"
Content-class: urn:content-classes:message
Subject: RE: Hostnames, Filer Names, and Cluster Names... Case Sensitive or Not?
Date: Wed, 31 Oct 2007 11:58:00 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0648DE49@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03E9A407@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Hostnames, Filer Names, and Cluster Names... Case Sensitive or Not?
Thread-Index: Acgb7xtGuD+p+nu/Rs2bAITEGwg77QAAC8eg
References: <BB375AF679D4A34E9CA8DFA650E2B04E03E9A407@onstor-exch02.onstor.net>
From: "Jonathan Goldick" <jonathan.goldick@onstor.com>
To: "Chris Vandever" <chris.vandever@onstor.com>,
	"dl-Customer-Engineering" <dl-Customer-Engineering@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>
Cc: "Charissa Willard" <charissa.willard@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C81BEF.F909B5B4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

In SystemX I am planning on host and volume names being case insensitive
in all commands, although you can set the names to any variant of case
you want.  What this means is that you can create a filer name like
FilerHost1 but you cannot then create another called filerhost1.

While the Internet standard for DNS names is case sensitive this is just
too confusing to allow.  I strongly believe that we should define rules
of acceptable configuration that prevent customers from shooting
themselves in the foot...like the customer that deleted the wrong volume
last year because one was called vol1 and the other was Vol1.


_____________________________________________
From: Chris Vandever=20
Sent: Wednesday, October 31, 2007 11:52 AM
To: dl-Customer-Engineering; dl-Design Review
Cc: Charissa Willard; Brian DeForest
Subject: Hostnames, Filer Names, and Cluster Names... Case Sensitive or
Not?

We have two ECRs we'd like to get some feedback on:

*	#17831 (Gateway names should be case-insensitive)
*	#11325 ("vsvr move -f filername" is case sensitive, "vsvr set
vsvrname" is not)

Currently, filer names and cluster names are case sensitive, just like
the underlying hostname on which they are based in BSD.  Vsvr names and
CIFS share names are case insensitive, and are converted to upper case
before they are stored in the cluster database.

Convenience would dictate that filer names and cluster names be case
insensitive.  However, that imposes restrictions that do not exist for
the underlying hostnames in BSD.  Do we have customers who rely on the
names being case sensitive?  What do customers expect?

Thoughts?

ChrisV & Charissa


------_=_NextPart_001_01C81BEF.F909B5B4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Hostnames, Filer Names, and Cluster Names... Case Sensitive =
or Not?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">In SystemX I am planning on =
host and volume names being case insensitive in all commands, although =
you can set the names to any variant of case you want.&nbsp; What this =
means is that you can create a filer name like FilerHost1 but =
you</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">cannot</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">then =
create another called filerhost1.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">While the Internet standard for DNS names is case =
sensitive</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> this is =
just too confusing to allow</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">.&nbsp; I strongly believe that we should define =
rules of acceptable configuration that prevent customers from shooting =
themselves in the foot</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">&#8230;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">like the =
customer that deleted the wrong volume last year because one was called =
vol1 and the other was Vol1.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Chris Vandever<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Wednesday, October 31, 2007 11:52 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Customer-Engineering; dl-Design Review<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Cc:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Charissa Willard; Brian DeForest<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></SPAN></B><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"></FONT> <FONT SIZE=3D2 =
FACE=3D"Tahoma">Hostnames, Filer Names, and Cluster Names... Case =
Sensitive or Not?</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">We have two ECRs we&#8217;d like to get some =
feedback on:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">&#183;<FONT FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Arial">#17831 (Gateway names should be =
case-insensitive)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">&#183;<FONT FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">#11325 (&#8220;vsvr move =
-f filername&#8221; is case sensitive, &#8220;vsvr set vsvrname&#8221; =
is not)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Currently, filer names and cluster names are case =
sensitive, just like the underlying hostname on which they are based in =
BSD.&nbsp; Vsvr names and CIFS share names are case insensitive, and are =
converted to upper case before they are stored in the cluster =
database.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Convenience would dictate that filer names and cluster =
names be case insensitive.&nbsp; However, that imposes restrictions that =
do not exist for the underlying hostnames in BSD.&nbsp; Do we have =
customers who rely on the names being case sensitive?&nbsp; What do =
customers expect?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Thoughts?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">ChrisV =
&amp; Charissa</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C81BEF.F909B5B4--
